Skip to content

chore: drop * wildcard from CODEOWNERS to stop Dependabot review pings#36

Merged
hyperpolymath merged 1 commit into
mainfrom
chore/codeowners-drop-wildcard
May 14, 2026
Merged

chore: drop * wildcard from CODEOWNERS to stop Dependabot review pings#36
hyperpolymath merged 1 commit into
mainfrom
chore/codeowners-drop-wildcard

Conversation

@hyperpolymath
Copy link
Copy Markdown
Owner

The catch-all * @hyperpolymath line in CODEOWNERS causes GitHub to auto-request review on every Dependabot PR (since every PR touches at least one owned path under *). With the sole maintainer being the same user, those review requests are pure notification noise.

This drops the wildcard line while preserving any path-specific ownership and SPDX/license headers. Path-specific lines are intentional and stay.

Human PRs from collaborators still trigger path-owner review where applicable; Dependabot PRs typically only touch root manifest files which are no longer matched.

@hyperpolymath hyperpolymath reopened this May 14, 2026
@hyperpolymath hyperpolymath merged commit d6a9983 into main May 14, 2026
27 of 36 checks passed
@hyperpolymath hyperpolymath deleted the chore/codeowners-drop-wildcard branch May 14, 2026 12:25
hyperpolymath added a commit that referenced this pull request May 14, 2026


Replaces the local copy of `.github/workflows/hypatia-scan.yml` with the
canonical version from upstream main. The old copy had three issues that
combined to break every Dependabot PR:

1. `working-directory: \${{ env.HOME }}/hypatia\``, where `env.HOME`
   is not a GHA context — it evaluated to empty, so `cd /hypatia`
   failed and the scanner was never built.
2. `hypatia-cli.sh scan .` without `--exit-zero` — scanner exit-1 on
   findings short-circuited the rest of the step under `set -e`.
3. No baseline gate, so any pre-existing critical/high failed the build.

Upstream version:
- captures scanner exit code + stderr (visible on crash)
- falls back to `[]` on missing/invalid JSON
- reads `.hypatia-baseline.json` and fails only on NET-NEW critical/high
- scopes permissions narrowly (contents: read, pull-requests: write)
- marks the PR-comment step `continue-on-error: true` so Dependabot PRs
  (read-only token) don't fail on the unavoidable 403

Baseline file follows in a second commit on this branch — first we need
the new workflow to actually run and capture current findings.

Unblocks PR #36 (CODEOWNERS) which is stuck on this exact scan.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
hyperpolymath added a commit that referenced this pull request May 14, 2026


Replaces the local copy of `.github/workflows/hypatia-scan.yml` with the
canonical version from upstream main. The old copy had three issues that
combined to break every Dependabot PR:

1. `working-directory: \${{ env.HOME }}/hypatia\``, where `env.HOME`
   is not a GHA context — it evaluated to empty, so `cd /hypatia`
   failed and the scanner was never built.
2. `hypatia-cli.sh scan .` without `--exit-zero` — scanner exit-1 on
   findings short-circuited the rest of the step under `set -e`.
3. No baseline gate, so any pre-existing critical/high failed the build.

Upstream version:
- captures scanner exit code + stderr (visible on crash)
- falls back to `[]` on missing/invalid JSON
- reads `.hypatia-baseline.json` and fails only on NET-NEW critical/high
- scopes permissions narrowly (contents: read, pull-requests: write)
- marks the PR-comment step `continue-on-error: true` so Dependabot PRs
  (read-only token) don't fail on the unavoidable 403

Baseline file follows in a second commit on this branch — first we need
the new workflow to actually run and capture current findings.

Unblocks PR #36 (CODEOWNERS) which is stuck on this exact scan.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
hyperpolymath added a commit that referenced this pull request May 14, 2026
 (#37)

Workflow-only commit; baseline follows after the new workflow's first
run captures findings. Unblocks #36.

---------

Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant